Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enip rust 3958 v13 #10186

Closed
wants to merge 9 commits into from
Closed

Conversation

catenacyber
Copy link
Contributor

@catenacyber catenacyber commented Jan 17, 2024

Link to redmine ticket:
https://redmine.openinfosecfoundation.org/issues/3958

Describe changes:

  • convert enip parser to rust
  • integer keywords now support hexadecimal notation

Alon the way, also

  • transactions are now bidirectional
  • there is a enip logger
  • gap support is improved with probing for resync
  • frames
  • events
  • enip_command keyword accepts now string enumeration as values.
  • more keywords

#10183 with SV test updated and doc for enip_command:list_identity

SV_BRANCH=pr/1585

OISF/suricata-verify#1585

catenacyber and others added 9 commits January 16, 2024 15:42
So that we can write enip.revision: 0x203

Ticket: 6645
Ticket: 6647

Allows keywords using integers to use strings in signature
parsing based on a rust enumeration with a derive.
Ticket: 6648

Like &0x40=0x40 to test for a specific bit set
Ticket: 6628

Document the generic detection capabilities for integer keywords.
and make every integer keyword pointing to this section.
Ticket: 3958

- transactions are now bidirectional
- there is a logger
- gap support is improved with probing for resync
- frames support
- app-layer events
- enip_command keyword accepts now string enumeration as values.
- add enip.status keyword
- add keywords :
    enip.product_name, enip.protocol_version, enip.revision,
    enip.identity_status, enip.state, enip.serial, enip.product_code,
    enip.device_type, enip.vendor_id, enip.capabilities,
    enip.cip_attribute, enip.cip_class, enip.cip_instance,
    enip.cip_status, enip.cip_extendedstatus
@suricata-qa
Copy link

Information:

ERROR: QA failed on SURI_TLPW2_autofp_suri_time.

field baseline test %
SURI_TLPW2_autofp_stats_chk
.uptime 181 194 107.18%

Pipeline 17559

@catenacyber
Copy link
Contributor Author

Rerunning CI with updated SV PR

Copy link

codecov bot commented Jan 17, 2024

Codecov Report

Attention: 1970 lines in your changes are missing coverage. Please review.

Comparison is base (6896a93) 82.12% compared to head (3d51b3f) 81.64%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #10186      +/-   ##
==========================================
- Coverage   82.12%   81.64%   -0.48%     
==========================================
  Files         975      983       +8     
  Lines      271724   273674    +1950     
==========================================
+ Hits       223151   223453     +302     
- Misses      48573    50221    +1648     
Flag Coverage Δ
fuzzcorpus 61.96% <35.40%> (-0.76%) ⬇️
suricata-verify 60.93% <42.41%> (-0.49%) ⬇️
unittests 62.43% <15.13%> (-0.41%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@catenacyber catenacyber mentioned this pull request Feb 12, 2024
@catenacyber
Copy link
Contributor Author

Rebased in #10377

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants